home *** CD-ROM | disk | FTP | other *** search
-
-
- OPUS 0.0 to OPUS 1.0
-
-
- TABLE OF CONTENTS
-
-
-
- I. INTRODUCTION .................................... 1
-
-
- II. FILE CHANGES ................................... 2
-
-
- III. STEP BY STEP INSTALLATION ..................... 3
-
-
- IV. DIFFERENCES BETWEEN OPUS 0.0 AND OPUS 1.0 ...... 4
-
-
-
-
-
-
- OPUS 0.0 to OPUS 1.00
-
- I. INTRODUCTION
- This document is intended for the experienced OPUS
- sysop who has been running OPUS 0.0. If you have not
- run OPUS 0.0 before, this document is not for you. It
- assumes you already know OPUS.
-
- The differences between the two versions are covered
- and how to quickly convert to the new system. If all
- goes well, you should have OPUS 1.00 functional within
- two hours. Setup of netmail is covered in the main
- OPUS documentation. After you finish your conversion,
- refer to it to set up netmail.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 1 -
-
-
-
- II. FILE CHANGES
-
- This section describes the changed files for converting
- to OPUS 1.00.
-
- A. CHANGED FILES
-
- 1. OPUS.EXE
-
- 2. OPUS.CTL
-
- 3. OPUS_CTL.EXE
-
- 4. OPUSGRAF.EXE
-
- 5. Menu files (???PRIV.BBS and ????PRIV.BBS)
-
- 6. Entire help files (normally C:\OPUS\HLP\*.BBS)
-
- 7. Some support display files (normally
- C:\OPUS\MISC\*.BBS
-
- B. DELETED FILES
-
- 1. MAIL.SYS
- (may be used by other utilities)
-
- 2. AREAS.BBS
- (may be used by other utilities)
-
- C. NEW FILES
-
- 1. ECHO.CTL
- (If you run internal echomail processing with OPUS)
-
- 2. OKFILE.LST
- (or other name determined by OPUS.CTL) - lists files
- you allow to be file requested. If it does not show
- up here, OPUS will not allow it to be requested.
-
- 3. ABOUT.LST
- (or other name determined by OPUS.CTL) - gives
- information about your BBS if user does a file
- request of the name ABOUT.
-
- 4. MASTER.LST
- (or other name determined by OPUS.CTL) - a list of
- all files available for file request when user does
- a file request of the name FILES.
-
-
-
-
-
-
-
-
- - 2 -
-
-
-
- III. STEP BY STEP
-
- Detailed step by step upgrade instructions are included
- with your OPUS kit in a file called QUICK_KIT.DOC.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 3 -
-
-
-
- IV. SUMMARY OF FUNCTIONAL CHANGES FROM OPUS 0.0 TO OPUS
- 1.0
-
- This section is not intended to give comprehensive detail
- on the changes. It simply highlights them. Detailed
- information is contained elsewhere in the main
- documentation and the OPUS.CTL file.
-
- A. OUTBOUND MAIL
- OPUS now will send outbound mail any time of the day.
- It will accept and process file requests. It will not
- send file requests.
-
- B. MATRIX ATTRIBUTES: ASSUMPTIONS AND OPTIONS
- Several new assumptions and options have been added.
- These concern the attributes of a message created by
- OPUS. A minimum privilege level can be assigned to
- each option. Detailed information is contained in the
- OPUS.CTL file.
-
- C. FORWARD THAN KILL COMMAND
- The FK command allows you to forward a message, then
- kill the original.
-
- D. EXTERNAL PROGRAMS FOR FILE TRANSFER
- There is more flexibility for external programs that
- handle file transfer. No protocol type is hard-coded.
- You have ten (10) "slots" available for file transfer
- protocol programs.
-
- E. SYSOP-IS-NEXT-KEY
- When a caller is on-line, the "S" key turns on/off a
- flag that tells Opus not to let any more callers on-
- line. In other words, Opus will hold the system for
- you.
-
- F. INTERNAL VIDEO CODES
- New embedded codes allow you to specify color
- attributes within a .BBS file. That allows one file to
- replace the former .BBS/.GBS combination. The old
- method is still supported.
-
- G. ORPHAN COMMAND
- This command has been eliminated in the Files Area
-
- H. EXTERNAL FILE MANAGEMENT OPTION
- You may link an external file manager directly into the
- File area menu.
-
-
-
-
-
-
-
-
-
- - 4 -
-
-
-
- I. CARRIER LOSS HANDLING
- OPUS can act as a watchdog and reboot after carrier
- loss when an external program is invoked.
-
- J. VIDEO METHOD
- Increased flexibility has been added for the local
- console video output method to allow optimization on
- certain computer types.
-
- K. LAN SUPPORT
- OPUS.EXE can now be kept on a server
-
- J. EXTERNAL MESSAGE MANAGEMENT
- You may link an external message manager directly into
- the Message area menu.
-
- K. ZONE COMMAND
- This command is no longer supported in the message area
- menu.
-
- L. CTL/PRM CHECK
- OPUS alarms if there is a date/time mismatch indicating
- you forgot to compile the control file.
-
- M. TIME AND DATE DISPLAY FORMAT FLEXIBILITY
- You can control how dates/times are displayed in
- messages
-
- N. TIME AND DATE STORAGE FORMAT
- There has been a change in the internal date/time
- format of message files (*.MSG).
-
- O. EXPANDED MULTITASKER SUPPORT
- In addition to DoubleDOS, Opus now supports several
- other operating system enhancement programs.
-
- P. DOS GATEWAY
- You can execute a dos command from the local sysop menu
- when OPUS is waiting for a caller.
-
- Q. TASK NUMBERS
- OPUS now allows you to specify a task number. This
- will affect the name of certain files. It makes it
- easier to run multiple copies of OPUS on the same PC.
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 5 -
-
-
-
- R. NO CHAT DURING GBS/BBS FILE EXECUTION
- Due to the overlay structure, you cannot go into chat
- when any GBS/BBS file is executing. OPUS sends a
- warning to the local console, if you try to do this.
-
- S. FORCED EVENTS
- Events may be declared as forced. If a mail transfer
- carries you past the time of a forced event, it will be
- executed anyway.
-
- T. MESSAGES FROM DISK FILES
- You may create a message from a disk file. This is
- handy for a welcome message to new users and similar
- such things.
-
- U. DISK SPACE ALARM
- If disk space gets low in the primary areas for
- netmail, OPUS sounds an alarm.
-
- V. MULTIPLE MATRIX ADDRESSES
- You may declare up to fifteen (15) matrix addresses.
- Only one address will be associated with outbound
- traffic. This is handy for hosts and hubs.
-
- W. UPLOADED MESSAGES
- Users may upload a message directly. Ansi graphics are
- allowed with this method if the message area is not an
- ECHO area.
-
- X. EXTERNAL MESSAGE EDITOR
- An external message editor may be declared to replace
- the normal line oriented editor. OPUS will
- automatically quote any message if you reply with and
- external editor.
-
- Y. NEW EMBEDDED COMMAND: GoTo
- Allows jumps to skip a section of GBS/BBS file.
-
- Z. ASYNCH PORTS
- You may specify any of sixteen (16) asynch ports
- provided your FOSSIL program supports such a port.
-
- AA. KEYBOARD COMMANDS
- The K key replaces the former ^K key for local keyboard
- command. The M key replace the former ^U key. It
- calls a matrix menu for performing many matrix
- operations.
-
-
-
-
-
-
-
-
-
-
- - 6 -
-
-
-
- BB. FILES.BBS WILDCARDS
- Files listed with wildcards may be downloaded
-
- CC. FIDO STYLE QUESTIONNAIRE COMMANDS NO LONGER
- SUPPORTED
- The Fido style questionnaire embedded commands are no
- longer supported.
-
- DD. FIDO ".HLP" EXTENSIONS NO LONGER SUPPORTED
-
- EE. EVENT MANAGER SUPPORTS DAY OF THE WEEK
-
- FF. OUTSIDE EMBEDDED COMMAND SUPPORTS PARAMETERS
- The ^OC command now supports passing parameters for
- external programs.
-
- GG. INTERNAL ZMODEM PROTOCOL
- This fast robust protocol is supported as an internal
- protocol for file transfer as well as for netmail (when
- communicating with another OPUS)
-
- HH. NEW NETMAIL HANDSHAKE
- The YooHoo (c) handshake protocol is implemented. This
- allows future provision for passwords and recognition
- of a system that can use Zmodem. It is compatible with
- most other non-OPUS netmail systems.
-
- II. ZONE AND POINT ADDRESSING IMPLEMENTATION
- These are extensions to the NET/NODE addressing scheme
- to allow support for INTERNATIONAL as well LOCAL mail
- addressing.
-
- JJ. EXTRA SUPPORT FOR EXTERNAL ECHOMAIL PROGRAMS
- OPUS can optionally create a log of message areas to
- which it tosses echomail. This will allow external
- programs to process only those areas that have changed.
-
- KK. EXTENDED MODEM SUPPORT
- Higher baud rates as well as constant baud rates are
- supported for compatibility with the new higher speed
- modems. Several forms of flow control support are now
- supported
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 7 -
-
-
-
- LL. LASTREAD POINTERS FOR SYSOP
- The lastread pointers for the first user in the USER
- file are handled differently. This means that lastread
- pointers are retained for all areas, not just the eight
- allowed for users. It also means the lastread pointers
- are the same for local keyboard mode as well as remote
- access mode.
-
- MM. DEFAULT OF USER TO AREA 1 ON CARRIER LOSS
- If carrier is dropped, the user record is set to area
- number 1.
-
- NN. CONTENTS COMMAND DISPLAYS DATE/TIME
- The C)ontents command in the file area will display the
- date/time of each file contained in an archive.
-
- OO. LOGON TIME LIMIT CONFIGURABLE
- You may specify a different logon time limit for users.
-
- PP. CONFIGURABLE "LOOKING BUSY" SUPPORT
- You may specify the specific string to cause a modem to
- look busy. This includes DTR manipulation. The added
- flexibility is useful for the new higher speed modems.
-
- QQ. COMPLETE INTERNAL ECHOMAIL SUPPORT
- OPUS can do complete internal echomail support:
- tossing, scanning, and duplicate message killing.
-
-
- RR. DIALING SCRIPT SUPPORT
- You may write a dialing script to replace the phone
- number in a node list. This is useful for accessing
- certain networks.
-
- SS. EXPORT MESSAGE TO DISK
- Messages may be written to disk in an ASCII format by
- selecting the X)port command from the Message area
- menu.
-
- TT. ENHANCED EMBEDDED USER INPUT COMMAND ACCEPTS <ENTER>
- When creating questions or menus with embedded
- commands, they can now be configured to accept the
- <enter> key as a valid response.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - 8 -